Yes @kahgoh, as mentioned earlier, there were tests.toml files that needed syncing. I wasn’t aware that test files require manual updates, but after your reply, I started manually updating the tests for each exercise. So far, I’ve completed 3 exercises and have 4 more to go. Once I finish, I plan to push changes for all 7 exercises together.

I wanted to clarify if I should add my name to the list of contributors for these exercises. While I’ve manually added tests based on the canonical-data file from the problem-specifications repo, this is more of a sync update. The last time I changed the reference solution and starting point for an exercise, I did add my name. Should I do so here as well?

Regarding the PR structure, I’m considering whether to handle everything in this PR or split it into multiple PRs. Keeping this PR focused on documentation updates and creating separate PRs for the test updates could make the changes more organized and easier to review. Additionally, while the work would remain the same, this approach might better align with contributing guidelines. Let me know your thoughts on the best approach.

For the contributors, yes, feel free to add yourself to the contributors list where you've updated the test as you're doing that manually.

For the PR structure, I'd go with splitting as well. In addition to keeping it organized, it also allows the Markdown file updates to go through while we do the test updates.

Perfect! That aligns exactly with my thoughts. I'll close this PR altogether and create a single PR for all the documents and separate PRs for the tests of each exercise.

I am hereby closing this PR as the other PRs discussed within it have already been raised.